home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Atari Mega Archive 1
/
Atari Mega Archive - Volume 1.iso
/
lists
/
gem
/
l_1199
/
1163
< prev
next >
Wrap
Internet Message Format
|
1994-08-27
|
3KB
From: Mark.Baker@mettav.exnet.com (Mark Baker)
Date: 29 Jul 94 18:42:58
Message-Id: <UUCP.775621734@mettav>
Subject: Re: app_defs
To: gem-list@world.std.com (gem-list@world.std.com)
Precedence: bulk
Chris:
> I'm uncertain about the idea of application-types... How many dtp
> packages or word processors is a user likely to have? Would it really
> be *useful* to be able to define a different key for 'Quit' just for
> image processing apps?
But you might well want different default fonts, and different keys for select
all perhaps.
>> Preclude discussion and you end up with
>> the type of standards comittees you often get in industry: where
>> everyone is just trying to make THEIR PRODUCT the standard, regardless
>> of its merits.
>
> Hmmm. This sounds mighty similar to the gem toolkit discussion/flame
> fest.
But it is better to discuss it than to simply vote where people are voting in a
way that makes their library conform and not others - I do it this way, why
can't everyone else - by discussing it we will hopefully end up with a standard
that has the best features of all libraries and will not require other
libraries to change completely to copy one. Mind you amicable discussion would
be nicer.
Kevin:
>> Dialogs in Windows (on/off)
> I assume by this you mean wether the dialogs are modeless or not (since
> you can't do modeless dialogs that aren't in windows without a lot of
> hacking)? If that's the case then I don't think this is something you can
> really switch on or off. Nor can I see any reason why a user would want
> it off.
>
I can see a reason. If you have LTMF installed it blits to restore the screen
when dialogues are closed (on form_dial(FMD_FINISH...)) which is much faster
than redrawing everything - even if all the other applications blit to redraw
-as you would with non-modal ones. That said I still prefer non-modal ones but
the speed is noticable and I might well prefer modal dialogues on a standard
ST.
Tim:
>> Ok, then use XAES. We allow you to drag/resize/scroll/close/etc windows
>> in the background under normal TOS, even TOS 1.0.
>
> How do you do this? HOW? You can't get anything other than WM_TOPPED
> messages to background windows under normal TOS.
>
> Oh, but you're replacing parts of AES, aren't you. Vector-stealing.
> Icky. Isn't the exception stack frame different on the 68030 compared to
> the 68000?
Actually they don't have to do that, because they're drawing the window borders
themselves in a (to the aes) featureless window (and therefore they don't look
anything like standard windows -and he's saying _we_ don't want standards? :)
so any click on any gadget will get a WF_TOPPED event.
As for exception frames, you're right but you don't necessarily have to worry
about this for vector-stealing, it depends on what exactly you intend to do
with the vector.